feat: EAS build with GitHub Actions#124
Merged
Merged
Conversation
💯 Test Coverage
😎 Tests Results
👀 Tests Details • (50%)
|
|
This PR is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 14 days |
asdolo
added a commit
that referenced
this pull request
Sep 19, 2025
…ions feat: EAS build with GitHub Actions
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this do?
Implement EAS local builds on Github-hosted runners.
Why did you do this?
EAS has a quota of 15 builds per month, which might be a low limit for some projects.
Who/what does this impact?
Build and deploy processes and times.
How did you test this?
We implemented this new workflow in a couple of projects and made adjustments.
Notes:
Screenshots / Previews